Incorporate suggestions from restoration of Target Size (Enhanced) Understanding #4589
Conversation
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| <p>The targets on a screen can have different purposes and uses, and this Success Criterion specifies how each is to be handled.</p> | ||
| <p><strong>Equivalent targets:</strong> If there is more than one target on a screen that performs the same action, only one of the targets need to meet the target size of 44 by 44 CSS pixels.</p> | ||
| <p><strong>Inline:</strong> Content displayed can often be reflowed based on the screen width available. This is known as responsive design and makes it easier to read since you do not need to scroll both horizontally and vertically. In reflowed content, the targets can appear anywhere on a line and can change position based on the width of the available screen. Since targets can appear anywhere on the line, the size cannot be larger than the available text and spacing between the sentences or paragraphs, otherwise the targets could overlap. It is for this reason targets which are contained within one or more sentences are excluded from the target size requirements.</p> | ||
| <p><strong>Inline:</strong> Content displayed is often designed to reflow based on the screen width available. This is known as responsive design and makes it easier to read since you do not need to scroll both horizontally and vertically. In reflowed content, the targets can appear anywhere on a line and can change position based on the width of the available screen. Since targets can appear anywhere on the line, the size cannot be larger than the available text and spacing between the sentences or paragraphs, otherwise the targets could overlap. It is for this reason targets which are contained within one or more sentences are excluded from the target size requirements.</p> |
There was a problem hiding this comment.
while this is original text, i'm not a super-fan of the awkward "Content displayed". wonder if just dropping "displayed" would make this sound less clunky. or, if it must retain the distinction (so it's not confused with audio content, for instance), maybe changing it to "Visible content" or even at the very least "Displayed content"
There was a problem hiding this comment.
The inline description in https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum is significantly different, and doesn't have this awkward phrase. As a lite change, I suggest a slight riff on its first sentence:
| <p><strong>Inline:</strong> Content displayed is often designed to reflow based on the screen width available. This is known as responsive design and makes it easier to read since you do not need to scroll both horizontally and vertically. In reflowed content, the targets can appear anywhere on a line and can change position based on the width of the available screen. Since targets can appear anywhere on the line, the size cannot be larger than the available text and spacing between the sentences or paragraphs, otherwise the targets could overlap. It is for this reason targets which are contained within one or more sentences are excluded from the target size requirements.</p> | |
| <p><strong>Inline:</strong> The success criterion does not apply to inline targets in sentences or blocks of text. Content is often designed to reflow based on the screen width available. This is known as responsive design and makes it easier to read since you do not need to scroll both horizontally and vertically. In reflowed content, the targets can appear anywhere on a line and can change position based on the width of the available screen. Since targets can appear anywhere on the line, the size cannot be larger than the available text and spacing between the sentences or paragraphs, otherwise the targets could overlap. It is for this reason targets which are contained within one or more sentences are excluded from the target size requirements.</p> |
|
@filippo-zorzi can you please check for any rationale for why example 3 was removed? |
|
In the PR #3638 @bruce-usab made a comment on the third esample:
Since I wanted to bring over all the comments from the other PR, I had to find a way to highlight and remember the needed revision of the third example. For sure this method is not the proper way to bring over a discussion given the fact that I forgot about that on last Friday meeting. That commit is made to be changed. |
PR for #3864
Adding the suggestion presented in this PR #3638 by @detlevhfischer, @frankie-wolf and @bruce-usab.